System and method of wireless device activity messaging

ABSTRACT

A method and system of reachability indication between a wireless device and at least one push server, the method comprising the steps of: sending device status information from the wireless device to the at least one push server; and receiving the status information at the at least one push server; wherein the at least one push server is enabled to selectively start and stop serving the wireless device on the basis of the status information. The method further comprises sending status information to a packet data serving node that stores a list of push servers associated with a wireless device, and having the packet data serving node forward the status information to the push server. The system and method further includes selectively starting and stopping the serving of the wireless device by the push server during a voice call.

RELATED APPLICATIONS

The present application is a continuation of U.S. application Ser. No.10/836,245, filed May 3, 2004, which claims priority from U.S.provisional application Ser. No. 60/468,310 filed 6 May 2003. Thecontents of U.S. application Ser. No. 10/836,245 and U.S. provisionalapplication Ser. No. 60/468,310 are incorporated herein by reference.

BACKGROUND

1. Field of the Invention

This invention relates to wireless data devices that access a wirelessnetwork, and to infrastructures that route packet data traffic betweendata servers and wireless data devices within the wireless network. Thewireless data devices referred herein include Personal DigitalAssistants, mobile communication devices, cellular phones, and wirelesstwo-way communication devices that have packet data processingcapability and intended to be used in wireless networks.

2. Description of the Related Art

In a CDMA2000 (1× Code Division Multiple Access) network, the networktypically requires a wireless data device to send a power-upregistration when powering up. Similarly, the network requires thedevice to send an explicit power-down registration message when itpowers down for any reason. In this way the CDMA2000 network knows thatthe wireless data device does not require any services and is no longerreachable.

For wireless data devices that support push services, there may be oneor more push servers running on different networks managed by differententities. These push servers deliver information such as notification,data and multimedia content to the wireless devices via the wireless IPnetwork. The device's reachability information known to the CDMA2000network may not be available to the push servers. When a device is notavailable, the data servers may keep pushing data traffic to anunreachable device, resulting in a waste of network bandwidth and thestarvation of available devices.

Packet data services are integrated on top of circuit switched servicesin CDMA2000 networks. Another problem may arise when a wireless datadevice does not support concurrent data services and voice services. Forinstance, when the device is in a voice call, it is unable to accept adata call. In this situation, it is desirable that the data servers stoppushing data to the device temporarily.

SUMMARY

One method which mitigates unnecessary data traffic on the CDMA2000network includes sending device status information from a wireless datadevice to its push servers so that the push servers know when to startand when to stop serving the wireless data device.

Another solution is to let a wireless data push server register with thepacket data serving node (PDSN) and specify the wireless devices thatare associated with it. When the PDSN is informed of a change in devicestatus information, it notifies all the registered push serversassociated with that wireless data device.

Alternatively, the PDSN may gather the push server informationautomatically by examining the header of incoming packet data designatedfor a specific wireless data device.

After the push servers are notified of the status change of the wirelessdata devices by the PDSN, the push servers can start or stop pushingdata traffic to the wireless networks accordingly. In this way, the datatraffic on the wireless network can be reduced to save networkresources.

The present invention therefore provides a method for reachabilityindication between a wireless device and at least one push server, themethod comprising the steps of: sending device status information fromthe wireless device to the at least one push server; and receiving thestatus information at the at least one push server; wherein the at leastone push server is enabled to selectively start and stop serving thewireless device on the basis of the status information.

The present invention further provides a method for reachabilityindication between a wireless device and at least one push server, themethod comprising the steps of: sending device status information fromthe wireless device to a packet data serving node; receiving the statusinformation at packet data serving node and sending from the packetserving node a status message to the at least one push server, thestatus message corresponding to the status information; receiving thestatus message at the at least one push server; wherein the at least onepush server is enabled to selectively start and stop serving thewireless device on the basis of the status information.

The present invention still further provides a method for reachabilityindication between a wireless device and at least one push server, thewireless device being unable to support simultaneous voice and datacalls, the method comprising the steps of: sending voice callinformation from a mobile switching center to a base station controller;sending from the base station controller to a packet data serving node adata status notification; receiving the data status notification at thepacket data serving node and sending to the at least one push serverstatus information; and receiving the status information at the at leastone push server; wherein the at least one push server is enabled toselectively start and stop serving the wireless device on the basis ofthe status information.

The present invention yet further provides a push server enabled toselectively start and stop serving a wireless device on the basis ofreceived status information, said push server comprising: a transceiverenabled to receive status information about the wireless device; aprocessor enabled to interpret status information about the wirelessdevice and to start or stop serving the wireless device based on thestatus information; and a storage subsystem capable of storing thestatus information for the wireless device.

The present invention further provides a packet data serving nodecomprising: a processor; a first transceiver interface for communicatingwith a base station controller and receiving status information for awireless device; a second transceiver interface for communicating with anetwork and for transmitting status information for the wireless device;and a data storage subsystem, said data storage subsystem including: arecords storage, said records storage storing data associating awireless device with at least one push server, wherein said recordsstorage is accessible by said processor upon receipt by said firsttransceiver interface of the status information for the wireless device,allowing the processor to forward the status information to the at leastone push server associated with the wireless device.

The present invention further provides a base station controllercomprising: a processor; a first transceiver interface for communicatingwith a mobile switching center and receiving voice call information fora wireless device; a second transceiver interface for communicating witha packet data serving node and for transmitting status information forthe wireless device; and a data storage subsystem, said data storagesubsystem including: a records storage, said records storage storingdata indicating whether a wireless device can support concurrent voiceand data calls and whether the wireless device is in a voice call;wherein said records storage is accessible by said processor uponreceipt by said first transceiver interface of the voice callinformation for the wireless device, allowing the processor to forwardthe status information to the packet data switching network.

The present invention further provides a wireless data devicecomprising: a processor, a user interface communicating with theprocessor for providing input to the wireless data device, a transceiverinterface controlled by said processor for communicating with a wirelessnetwork, a storage subsystem communicating with said processor andhaving information about push servers serving said wireless data device,wherein said wireless data device communicates status information to thepush servers serving the wireless devices using said transceiver oversaid wireless network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary CDMA2000 wireless data networksystem in accordance with the present application and with which thevarious embodiments of the method of the instant application maycooperate;

FIG. 2 is a block diagram of an exemplary wireless data device for usewith the method of the present application;

FIG. 3 is a block diagram of an exemplary push server for use with themethod of the present application;

FIG. 4 is a block diagram of an exemplary PDSN for use with the methodof the present application;

FIG. 5 is a block diagram of an exemplary BSC for use with the method ofthe present application;

FIG. 6 illustrates various embodiments of the techniques of the presentapplication in terms of a flow chart;

FIG. 7 illustrates in greater detail the signaling and data flow betweenthe wireless data device, and two push servers in accordance with afirst embodiment of a method of the present application;

FIG. 8 illustrates in greater detail the signaling and data flow amongthe wireless data device, PDSN and two push servers in accordance with asecond embodiment of the method of the present application; and

FIG. 9 is a detailed signal flow diagram illustrating the signaling,voice and data flow among the wireless data device, BSC, MSC, PDSN andpush servers in accordance with a third embodiment of the a method ofthe present application.

The same reference numerals are used in different Figures to denotesimilar elements.

DETAILED DESCRIPTION

Referring to FIG. 1, FIG. 1 is a block diagram of an exemplary CDMA2000wireless data network system in accordance with the present applicationand with which the various embodiments of the method of the instantapplication may cooperate. FIG. 1 shows a block diagram of a wirelessdata device 10, an exemplary 1× Code Division Multiple Access (CDMA2000)mixed circuit switched and packet switched network 20, a Public SwitchedTelephone Network (PSTN) 30, Internet 40 and push servers 50 with whichthe instant techniques of this application may cooperate. The wirelessdata device 10 is preferably a two-way communication device having dataand/or voice communication capabilities.

CDMA2000 network 20 includes mixed circuit and packet switchedcomponents—Base Transceiver Subsystem (BTS) 22 and Base StationController (BSC) 24, a circuit switched only component—Mobile SwitchingCentre (MSC) 26, and a packet switched only component—Packet DataServing Node (PDSN) 28.

Operationally, mobile device 10 communicates wirelessly with BTS 22 andBSC 24 to gain access to circuit switched services provided by MSC 26,such as voice and short message service (SMS) via PSTN 30.

Mobile device 10 also communicates wirelessly with BTS 22 and BSC 24 togain access to packet data services provided by PDSN 28, such as e-mail,wireless application protocol (WAP), and other data services viaInternet 40.

FIG. 2 is a block diagram of an exemplary wireless data device for usewith the method of the present application. Reference is still made toFIG. 1 for individual components within wireless network 20. Thewireless data device 10 is preferably a two-way communication devicehaving at least data or data/voice communication capabilities. Where thedevice 10 is enabled for two-way communications, the device willincorporate a processor 100, a storage subsystem 102, a transceiversubsystem 104 and a user interface module 106. The microprocessor 100controls the overall operation of the wireless data device.Communication functions, including signaling between wireless datadevice 10 and wireless network 20, signaling between wireless datadevice 10 and push servers 50, and data/voice communications, areperformed through the transceiver subsystem 104. The microprocessor 100also interacts with further device subsystems such as the storagesubsystem 102 and the user interface module 106. In CDMA2000 network,signaling between wireless data device 10 and wireless network 20, forinstance, includes power up and power down registrations. Users maycommand the operation of the wireless data device 10 through the userinterface module 106, for instance power up and power down the wirelessdata device 10, making data and/or voice calls.

The present method and application provide for signaling betweenwireless data device 10 and push servers 50 that includes conveyingstatus information about wireless data device 10 through a Data ActiveMessage 60 and Data Inactive Message 66.

A predetermined set of applications that control basic deviceoperations, including at least data communication applications forexample, will normally be installed on the device 10 during manufacture.A set of applications that may be loaded onto the device includes, butis not limited to e-mail, calendar events, appointments, browser andtask items. Such applications would have the ability to send and receivedata items, via the CDMA2000 network 20 and Internet 40 (not shown), toand from push server 50. For voice communications, device 10communicates with PSTN 30 (not shown) via the CDMA2000 network 20.

When the wireless data device 10 powers up, it sends a power upregistration to BSC 24. When the required power up registration has beencompleted, the wireless data device 10 may send and receivecommunication signals over CDMA2000 network 20.

When the wireless data device 10 powers down, it sends a power downregistration to BSC 24. When the required power down registration hasbeen completed, the CDMA2000 network 20 stops serving the wireless datadevice 10.

FIG. 3 is a block diagram of an exemplary push server for use with themethod of the present application. The push server 50 incorporates atleast one microprocessor 200, a storage subsystem 202, and a transceiversubsystem 204.

The microprocessor 200 controls the overall operation of the pushserver. Microprocessor 200 interacts with storage subsystem 202, andtransceiver subsystem 204. Communication functions, including signalingbetween push server 50 and wireless network 20, signaling between pushserver 50 and wireless data device 10, and data communications, areperformed through the transceiver subsystem 204. Signaling between pushserver 50 and wireless network 20 as well as signaling between pushserver 50 and wireless data device 10 include, but are not limited to,receiving status information about wireless data device 10. Further, aData Active Message 60 and Data Inactive Message 66 are sent to pushserver 50.

Push server 50 communicates with the wireless network 20 and withwireless data device 10 via Internet 40, as seen in FIG. 1.

FIG. 4 is a block diagram of an exemplary PDSN for use with the methodof the present application. Operationally it includes at least oneprocessor 300, a storage subsystem 302, and two transceiver interfaces304 and 306. The first transceiver interface 304 is used to receivestatus information of wireless data device 10 (not shown). In presentthe method and application, this includes a Data Active Notification 68or Data Inactive Notification 72 from BSC 24. These messages are used toindicate whether the wireless data device 10 will accept data using theData Active Notification 68, or will not accept data using the DataInactive Notification 72.

The second transceiver 306 is used to send information to push server50, as seen in FIG. 1. Using the present method and application,transceiver 306 can include a Data Active Message 60 or a Data InactiveMessage 66 sent to push server 50 via internet 40, as illustrated inFIG. 1. These messages tell push server 50 that wireless data device 10will accept data (Data Active Message 60) or not accept data (DataInactive Message 66).

In one embodiment, Storage subsystem 302 stores a system record 308.Each system record 308 represents all information for one wireless datadevice 10 and includes a device identifier field 308B to storeidentifier information for a wireless data device 10. Record 308 furtherpreferably includes a device status field 308D, as well as push serveridentifier field 308F for identifying all push servers 50 associatedwith wireless data device 10.

Processor 300 controls overall operation of PDSN 28. When a Data ActiveNotification 68 arrives at transceiver interface 304, the processor 300examines its system record 308 stored in storage subsystem 302 andretrieves all of the push server identifiers stored in push serveridentifier field 308F associated with the wireless data device 10, aslocated based on device identifier field 308B. Processor 300 sends outData Active Message 60 to all the push servers 50 (not shown) viatransceiver interface 306 and Internet 40 on behalf of wireless datadevice 10, after which all push servers may commence serving thewireless data device 10 by pushing data traffic onto wireless network20. The device status field 308D is updated accordingly.

Similarly when a Data Inactive Notification 72 arrives at transceiverinterface 304, the processor 300 examines its system record 308 storedin storage subsystem 302 and retrieves all push server identifiersstored in push server identifier field 308F associated with thatwireless data device 10, as located in device identifier field 308B.Processor 300 then sends out Data Inactive Message 66 to all pushservers 50 via transceiver interface 306 and internet 40 on behalf ofwireless data device 10, after which all push servers may safely ceaseserving the wireless data device 10 by terminating pushing data trafficonto the wireless network 20. The device status field 308D is updatedaccordingly.

FIG. 5 is a block diagram of an exemplary BSC for use with a furthermethod of the present application. It is applicable when both voice anddata capabilities are available on wireless data device 10 but voice anddata calls cannot be supported simultaneously. Operationally it includesat least one processor 400, a storage subsystem 402, and two transceiverinterfaces 404 and 406.

Storage subsystem 402 preferably has a system record 408. Each systemrecord 408 represents information for one wireless data device 10 andincludes a device identifier field 408B for storing identifiers forwireless data device 10. System record 408 further preferably includes adevice capability indicator field 408C (to indicate whether the deviceassociated with the device identifier field can support concurrent voiceand data calls), a device voice call status field 408D, as well asdevice data call status field 408F.

Processor 400 controls the overall operation of BSC 24. When a VoiceCall Notification 76 arrives at transceiver interface 404, the processor400 examines its system record 408 stored in storage subsystem 402 andfinds out through device capability indicator field 408C whether voicecall and data call can be supported simultaneously at wireless datadevice 10. If voice call and data call cannot be supportedsimultaneously at wireless data device 10, processor 400 further findsout through data call status field 408F whether there exist any on-goingpush services. If at least one on-going push service exists, processor400 will update voice call status field 408D, data call status field408F and send out a Data Inactive Notification 72 to PDSN 28 viatransceiver interface 406. PDSN 28 may update push server 50 with thenew status of wireless data device 10 accordingly as described abovewith reference to FIG. 4.

Similarly when a Voice End Notification 84 arrives at transceiver 404,the processor 400 examines its system record 408 stored in storagesubsystem 402 and finds out through device capability indicator field408C whether voice call and data call can be supported simultaneously atwireless data device 10. If device capability indicator field 408Cindicates that voice call and data call cannot be supportedsimultaneously by device 10, processor 400 further finds out throughdata call status filed 408F whether there existed any on-going pushservices at the time of the voice call setup. If any of these push dataservices existed, processor 400 will send out a Data Active Notification68 to PDSN 28 via transceiver interface 406. PDSN 28 may update pushserver 50 with the new status of wireless data device 10 accordingly asdescribed above with reference to FIG. 4. Voice call field 408D and datacall field 408F will be updated accordingly.

FIG. 6 illustrates a flow chart of the above embodiments of the presentapplication. If wireless data device 10 does not support voiceoperations, as identified in step 502, then data communications are thesole concern, and processing proceeds to step 504.

In step 504 a determination is made about whether the PDSN isincorporated into the present method and application. Without the PDSNbeing incorporated, the present method and application can be appliedbetween the wireless data device 10 itself and push server 50, which isdescribed below referring to FIG. 7. Conversely, if in step 504 PDSN 28is incorporated with the present method and application, the wirelessdata device 10 communicates with PDSN 28, which in turn communicateswith push servers 50, as detailed below referring to FIG. 8.

If wireless data device 10 supports both data calls and voice, as foundin step 502, a check in step 506 is made to determine whether wirelessdata device 10 supports concurrent voice and data calls. If wirelessdata device 10 does not support concurrent voice calls and data calls,the present method and application allows BSC 24 to communicate statusinformation to PDSN 28, and push servers 50, as detailed below in FIG.9.

If in step 506 it is determined that wireless data device 10 supportsconcurrent voice and data calls then push server 50 does not need tocease pushing data calls when the device is active, and the processcould end. However, as will be realized by those skilled in the art, themethods of FIG. 7 or 8 could still be used to disable pushing of datawhen the wireless data device 10 is turned off or out of radio coverage.

Referring now to FIG. 7, this Figure illustrates in greater detail thesignaling and data flow between wireless data device 10, and two pushservers 52 and 54 in accordance with a first embodiment of a method ofthe present application.

When the wireless data device 10 powers up, it notifies its data activestatus by sending Data Active Message 60A and Data Active Message 60B topush servers 52 and 54 respectively. After receiving Data Active Message60A and 60B, data servers 52 and 54 start serving the wireless datadevice 10. For example, user data 62A and 62B and server data 64A and64B can be exchanged between wireless data device 10 and push servers 52and 54 respectively.

When the wireless data device 10 powers down, it notifies its datainactive status by sending a Data Inactive Messages 66A and 66B to pushservers 52 and 54 respectively. After receiving Data Inactive Message66A and 66B, data server 52 and 54 stop serving the wireless data device10, preventing user data 62A and 62B from flowing in CDMA2000 network20.

The dashed curve lines of FIG. 7 within push server 52 are meant toindicate that the corresponding signaling and data traffic is betweenwireless data device 10 and push server 54, and does not actually flowthrough push server 52.

An improvement to the method of FIG. 7 is to have wireless data device10 only send one message, rather than a message to each of the pushservers 50. This saves battery life of wireless data device 10 andnetwork resources of wireless network 20. Reference is now made to FIG.8.

FIG. 8 illustrates in greater detail the signaling and data flow betweenwireless data device 10, PDSN 28 and two push servers 52 and 54 inaccordance with a second embodiment of the method of the presentapplication. When the wireless data device 10 powers up it notifies PDSN28 via BSC 24 with a Data Active Notification 68. PDSN 28 in turn sendsout Data Active Message 60A and 60B to push servers 52 and 54. As oneskilled in the art will realize, different number of push servers 50could exist for wireless data device 10, and if more push servers exist,Data Active Message 60 will be sent to these push servers as well.

As illustrated in FIG. 4, push servers 52 and 54 are registered withinserver identifier field 308F associated with the wireless deviceidentifier for wireless data device 10 at PDSN 28.

After push servers 52 and 54 receive Data Active Messages 60A and 60Brespectively, user data 62A and 62B and server data 64A and 64B can beexchanged between the wireless data device 10 and the push servers 52and 54 respectively. In CDMA2000 network, Data Active Notification 68may be associated with a Power Up Registration.

Likewise, when wireless data device 10 powers down, PDSN 28 is notifiedvia BSC 24 using a Data Inactive Notification 72. PDSN 28 then sends outData Inactive Message 66A and 66B to push servers 52, 54. In CDMA2000network, this Data Inactive Notification 72 may be associated with PowerDown Registration.

Based on the above, by using the method of FIG. 8, wireless data device10 does not have to send out multiple Data Active Messages and DataInactive Messages, thereby increasing its battery life, and reducingover the air traffic.

As with FIG. 7, the dashed lines flowing over push server 52 indicatethat the signaling and data traffic is between wireless data device 10and push server 54, and does not flow through push server 52.

In some cases it is desirable to further prevent push servers 50 frompushing data during a voice call when wireless data device 10 does notsupport concurrent voice and data calls. Reference is now made to FIG.9.

FIG. 9 illustrates a signal flow diagram showing the signaling, voiceand data flow among the wireless data device 10, BSC 24, MSC 26, PDSN 28and push servers 50 in accordance with a further embodiment of the amethod of the present application. FIG. 9 illustrates the interactionbetween a voice call and data call when voice and data cannot besupported simultaneously on wireless data device 10.

Initially the wireless data device 10 is in a data (active or dormant)mode of an on-going push service. When a voice call comes in, MSC 26notifies BSC 24 using Voice Call Notification 76. BSC 24 realizes thatwireless data device 10 is in a data (active or dormant) mode based onsystem record 408 through data call status field 408F as outlined abovewith regards to FIG. 5.

BSC 24 sends a Data Inactive Notification 72 to PDSN 28. After receivingData Inactive Notification 72, PDSN 28 notifies all push servers 50 thatregistered with it using a Data Inactive Message 66. All push servers 50stop pushing data onto the network for device 10 based on this message.

When the voice call ends, MSC 26 sends a Voice End Notification 84 toBSC 24. BSC 24 then notifies PDSN 28 using a Data Active Notification68. After receiving Data Active Notification 68, PDSN 28 sends out aData Active Message 60 to all push servers that are associated withwireless data device 10 and registered with PDSN 28. Push servers canthen start exchanging user data 62 and server data 64 with wireless datadevice 10.

The dashed curve line in MSC 26 indicates that the signaling and datatraffic are either between wireless data device 10 and push servers 50or between BSC 24 and PDSN 28. They do not flow through push data MSC26.

The embodiments of FIGS. 8 and 9 require all push servers 50 desirous ofcommunicating with wireless data device 10 to register with PDSN 28. Inan alternative embodiment, the PDSN may gather push server informationautomatically by examining the header of each packet data designated forthat wireless data device 10.

The embodiments described herein are examples of structures, systems ormethods having elements corresponding to elements of the application.This written description may enable those skilled in the art to make anduse embodiments having alternative elements that likewise correspond tothe elements of the application. The intended scope of the applicationthus includes other structures, systems or methods that do not differfrom the application as described herein, and further includes otherstructures, systems or methods with insubstantial differences from theapplication as described herein.

1. A packet data serving node enabled to communicate wireless devicedata status information for a wireless device registered with a wirelessnetwork, the packet data serving node comprising: (a) a processor; (b) afirst transceiver interface for communicating with a base stationcontroller and receiving data status information for the wirelessdevice, said data status information indicating if the wireless devicecan and cannot receive data; (c) a second transceiver interface forcommunicating with at least one push server and for transmitting datastatus information for the wireless device; and (d) a data storagesubsystem, said data storage subsystem including a records storage, saidrecords storage storing data associating a wireless device with at leastone push server, wherein said records storage is accessible by saidprocessor upon receipt by said first transceiver interface of the datastatus information for the wireless device, enabling the processor toforward the data status information to the at least one push serverassociated with the wireless device.
 2. The packet data serving node ofclaim 1, wherein the records storage includes: (a) a device identifierfield; (b) a device status field; and (c) a server identification fieldfor storing the at least one push server.
 3. The packet data servingnode of claim 2, wherein the at least one push server in the serveridentification field registers with the packet data serving node.
 4. Thepacket data serving node of claim 2, wherein the packet data servingnode monitors a header of incoming packet data designated for thewireless device to add the at least one push server to the serveridentification field.
 5. The packet data serving node of claim 1,wherein the data status information is received from the wirelessdevice.
 6. The packet data serving node of claim 1, wherein the datastatus information is received from a base station controller.
 7. Thepacket data serving node of claim 6, wherein the data status indicationindicates that the wireless device is in a voice call and is incapableof receiving simultaneous voice and data calls.
 8. A base stationcontroller adapted to provide data status information to selectivelystart and stop data transfer between a push server and a wireless deviceregistered with a wireless network, the base station controllercomprising: a) a processor; b) a first transceiver interface forcommunicating with a mobile switching center adapted to receive voicecall information for the wireless device; c) a second transceiverinterface for communicating with a packet data serving node and adaptedto transmit data status information for the wireless device; and d) adata storage subsystem, the data storage subsystem including a recordsstorage adapted to indicate whether a wireless device can supportconcurrent voice and data calls and whether the wireless device is in avoice call, wherein the records storage is accessible by the processorupon receipt by the first transceiver interface of voice callinformation for the wireless device, thereby allowing the processor toforward the data status information to the packet data serving node. 9.The base station controller of claim 8, wherein the records storageincludes: a) a wireless device identifier field; b) a wireless devicecapability indicator field; c) a voice status field; and d) a data callstatus field.
 10. The base station controller of claim 8, wherein thedata status information is one of a data active notification and a datainactive notification.
 11. The base station controller of claim 9,wherein the data call status field is adapted to store whether anyexisting ongoing push services exist.
 12. The base station controller ofclaim 8, wherein the records storage subsystem is updated upon receiptof new voice call information at said first transceiver interface.